Enter a type and click search.




Results for Magento\Payment\Model\Method\Adapter

File: vendor/amzn/amazon-pay-module/etc/di.xml

<virtualType name="AmazonFacade"
             type="Magento\Payment\Model\Method\Adapter">
    <arguments>
        <argument name="code" xsi:type="const">
            Amazon\Payment\Gateway\Config\Config::CODE
        </argument>
        <argument name="formBlockType" xsi:type="string">
            Magento\Payment\Block\Form
        </argument>
        <argument name="infoBlockType" xsi:type="string">
            Magento\Payment\Block\Info
        </argument>
        <argument name="valueHandlerPool" xsi:type="object">
            AmazonValueHandlerPool
        </argument>
        <argument name="validatorPool" xsi:type="object">
            AmazonValidatorPool
        </argument>
        <argument name="commandPool" xsi:type="object">
            AmazonCommandPool
        </argument>
    </arguments>
</virtualType>

This is a virtual type configuration.

This configuration is for the base area. Base area configurations will apply to all the sub-applications.

This virtualType configuration tells the Object Manager when a user wants a virtual AmazonFacade object that it should return a Magento\Payment\Model\Method\Adapter object.

This configuration tells the Object Manager that when a user wants a AmazonFacade object that the following arguments should be used in the foo object's constructor.

  • $code = Amazon\Payment\Gateway\Config\Config::CODE;
  • $formBlockType = "Magento\Payment\Block\Form";
  • $infoBlockType = "Magento\Payment\Block\Info";
  • $valueHandlerPool = new AmazonValueHandlerPool (...)
  • $validatorPool = new AmazonValidatorPool (...)
  • $commandPool = new AmazonCommandPool (...)
Results for Magento\Payment\Model\Method\Adapter

File: vendor/klarna/module-kp/etc/di.xml

<virtualType name="KPVirtual"
             type="Magento\Payment\Model\Method\Adapter">
    <arguments>
        <argument name="code" xsi:type="const">
            Klarna\Kp\Model\Payment\Kp::METHOD_CODE
        </argument>
        <argument name="valueHandlerPool" xsi:type="object">
            KPValueHandlerPool
        </argument>
        <argument name="commandPool" xsi:type="object">
            KPCommandPool
        </argument>
        <argument name="validatorPool" xsi:type="object">
            KPValidatorPool
        </argument>
        <argument name="formBlockType" xsi:type="string">
            Magento\Payment\Block\Form
        </argument>
        <argument name="infoBlockType" xsi:type="string">
            Klarna\Core\Block\Info\Klarna
        </argument>
    </arguments>
</virtualType>

This is a virtual type configuration.

This configuration is for the base area. Base area configurations will apply to all the sub-applications.

This virtualType configuration tells the Object Manager when a user wants a virtual KPVirtual object that it should return a Magento\Payment\Model\Method\Adapter object.

This configuration tells the Object Manager that when a user wants a KPVirtual object that the following arguments should be used in the foo object's constructor.

  • $code = Klarna\Kp\Model\Payment\Kp::METHOD_CODE;
  • $valueHandlerPool = new KPValueHandlerPool (...)
  • $commandPool = new KPCommandPool (...)
  • $validatorPool = new KPValidatorPool (...)
  • $formBlockType = "Magento\Payment\Block\Form";
  • $infoBlockType = "Klarna\Core\Block\Info\Klarna";
Results for Magento\Payment\Model\Method\Adapter

File: vendor/magento/magento2-base/dev/tests/integration/_files/Magento/TestModuleFakePaymentMethod/etc/di.xml

<virtualType name="Magento\TestModuleFakePaymentMethod\Gateway\Facade"
             type="Magento\Payment\Model\Method\Adapter">
    <arguments>
        <argument name="code" xsi:type="string">
            fake
        </argument>
        <argument name="formBlockType" xsi:type="string">
            Magento\Payment\Block\Form\Cc
        </argument>
        <argument name="infoBlockType" xsi:type="string">
            Magento\Payment\Block\ConfigurableInfo
        </argument>
        <argument name="valueHandlerPool" xsi:type="object">
            Magento\TestModuleFakePaymentMethod\Gateway\Config\ValueHandlerPool
        </argument>
        <argument name="validatorPool" xsi:type="object">
            Magento\TestModuleFakePaymentMethod\Gateway\Validator\ValidatorPool
        </argument>
        <argument name="commandPool" xsi:type="object">
            Magento\TestModuleFakePaymentMethod\Gateway\Command\CommandPool
        </argument>
    </arguments>
</virtualType>

This is a virtual type configuration.

This configuration is for the base area. Base area configurations will apply to all the sub-applications.

This virtualType configuration tells the Object Manager when a user wants a virtual Magento\TestModuleFakePaymentMethod\Gateway\Facade object that it should return a Magento\Payment\Model\Method\Adapter object.

This configuration tells the Object Manager that when a user wants a Magento\TestModuleFakePaymentMethod\Gateway\Facade object that the following arguments should be used in the foo object's constructor.

Results for Magento\Payment\Model\Method\Adapter

File: vendor/paypal/module-braintree-core/etc/di.xml

<virtualType name="BraintreeFacade"
             type="Magento\Payment\Model\Method\Adapter">
    <arguments>
        <argument name="code" xsi:type="const">
            PayPal\Braintree\Model\Ui\ConfigProvider::CODE
        </argument>
        <argument name="formBlockType" xsi:type="string">
            PayPal\Braintree\Block\Form
        </argument>
        <argument name="infoBlockType" xsi:type="string">
            PayPal\Braintree\Block\Info
        </argument>
        <argument name="valueHandlerPool" xsi:type="object">
            BraintreeValueHandlerPool
        </argument>
        <argument name="validatorPool" xsi:type="object">
            BraintreeValidatorPool
        </argument>
        <argument name="commandPool" xsi:type="object">
            BraintreeCommandPool
        </argument>
    </arguments>
</virtualType>

This is a virtual type configuration.

This configuration is for the base area. Base area configurations will apply to all the sub-applications.

This virtualType configuration tells the Object Manager when a user wants a virtual BraintreeFacade object that it should return a Magento\Payment\Model\Method\Adapter object.

This configuration tells the Object Manager that when a user wants a BraintreeFacade object that the following arguments should be used in the foo object's constructor.

File: vendor/paypal/module-braintree-core/etc/di.xml

<virtualType name="BraintreeApplePay"
             type="Magento\Payment\Model\Method\Adapter">
    <arguments>
        <argument name="code" xsi:type="const">
            PayPal\Braintree\Model\ApplePay\Ui\ConfigProvider::METHOD_CODE
        </argument>
        <argument name="valueHandlerPool" xsi:type="object">
            BraintreeApplePayValueHandlerPool
        </argument>
        <argument name="validatorPool" xsi:type="object">
            BraintreeApplePayValidatorPool
        </argument>
        <argument name="commandPool" xsi:type="object">
            BraintreeApplePayCommandPool
        </argument>
        <argument name="formBlockType" xsi:type="object">
            Magento\Payment\Block\Form
        </argument>
        <argument name="infoBlockType" xsi:type="string">
            PayPal\Braintree\Block\ApplePay\Info
        </argument>
    </arguments>
</virtualType>

This is a virtual type configuration.

This configuration is for the base area. Base area configurations will apply to all the sub-applications.

This virtualType configuration tells the Object Manager when a user wants a virtual BraintreeApplePay object that it should return a Magento\Payment\Model\Method\Adapter object.

This configuration tells the Object Manager that when a user wants a BraintreeApplePay object that the following arguments should be used in the foo object's constructor.

File: vendor/paypal/module-braintree-core/etc/di.xml

<virtualType name="BraintreeGooglePay"
             type="Magento\Payment\Model\Method\Adapter">
    <arguments>
        <argument name="code" xsi:type="const">
            PayPal\Braintree\Model\GooglePay\Ui\ConfigProvider::METHOD_CODE
        </argument>
        <argument name="valueHandlerPool" xsi:type="object">
            BraintreeGooglePayValueHandlerPool
        </argument>
        <argument name="validatorPool" xsi:type="object">
            BraintreeGooglePayValidatorPool
        </argument>
        <argument name="commandPool" xsi:type="object">
            BraintreeGooglePayCommandPool
        </argument>
        <argument name="formBlockType" xsi:type="object">
            Magento\Payment\Block\Form
        </argument>
        <argument name="infoBlockType" xsi:type="string">
            PayPal\Braintree\Block\GooglePay\Info
        </argument>
    </arguments>
</virtualType>

This is a virtual type configuration.

This configuration is for the base area. Base area configurations will apply to all the sub-applications.

This virtualType configuration tells the Object Manager when a user wants a virtual BraintreeGooglePay object that it should return a Magento\Payment\Model\Method\Adapter object.

This configuration tells the Object Manager that when a user wants a BraintreeGooglePay object that the following arguments should be used in the foo object's constructor.

File: vendor/paypal/module-braintree-core/etc/di.xml

<virtualType name="BraintreeVenmo"
             type="Magento\Payment\Model\Method\Adapter">
    <arguments>
        <argument name="code" xsi:type="const">
            PayPal\Braintree\Model\Venmo\Ui\ConfigProvider::METHOD_CODE
        </argument>
        <argument name="valueHandlerPool" xsi:type="object">
            BraintreeVenmoValueHandlerPool
        </argument>
        <argument name="validatorPool" xsi:type="object">
            BraintreeVenmoValidatorPool
        </argument>
        <argument name="commandPool" xsi:type="object">
            BraintreeVenmoCommandPool
        </argument>
        <argument name="formBlockType" xsi:type="object">
            Magento\Payment\Block\Form
        </argument>
        <argument name="infoBlockType" xsi:type="string">
            PayPal\Braintree\Block\Info
        </argument>
    </arguments>
</virtualType>

This is a virtual type configuration.

This configuration is for the base area. Base area configurations will apply to all the sub-applications.

This virtualType configuration tells the Object Manager when a user wants a virtual BraintreeVenmo object that it should return a Magento\Payment\Model\Method\Adapter object.

This configuration tells the Object Manager that when a user wants a BraintreeVenmo object that the following arguments should be used in the foo object's constructor.

File: vendor/paypal/module-braintree-core/etc/di.xml

<virtualType name="BraintreeAch"
             type="Magento\Payment\Model\Method\Adapter">
    <arguments>
        <argument name="code" xsi:type="const">
            PayPal\Braintree\Model\Ach\Ui\ConfigProvider::METHOD_CODE
        </argument>
        <argument name="valueHandlerPool" xsi:type="object">
            BraintreeAchValueHandlerPool
        </argument>
        <argument name="validatorPool" xsi:type="object">
            BraintreeAchValidatorPool
        </argument>
        <argument name="commandPool" xsi:type="object">
            BraintreeAchCommandPool
        </argument>
        <argument name="formBlockType" xsi:type="object">
            Magento\Payment\Block\Form
        </argument>
        <argument name="infoBlockType" xsi:type="string">
            PayPal\Braintree\Block\Info
        </argument>
    </arguments>
</virtualType>

This is a virtual type configuration.

This configuration is for the base area. Base area configurations will apply to all the sub-applications.

This virtualType configuration tells the Object Manager when a user wants a virtual BraintreeAch object that it should return a Magento\Payment\Model\Method\Adapter object.

This configuration tells the Object Manager that when a user wants a BraintreeAch object that the following arguments should be used in the foo object's constructor.

File: vendor/paypal/module-braintree-core/etc/di.xml

<virtualType name="BraintreeLpm"
             type="Magento\Payment\Model\Method\Adapter">
    <arguments>
        <argument name="code" xsi:type="const">
            PayPal\Braintree\Model\Lpm\Ui\ConfigProvider::METHOD_CODE
        </argument>
        <argument name="valueHandlerPool" xsi:type="object">
            BraintreeLpmValueHandlerPool
        </argument>
        <argument name="validatorPool" xsi:type="object">
            BraintreeLpmValidatorPool
        </argument>
        <argument name="commandPool" xsi:type="object">
            BraintreeLpmCommandPool
        </argument>
        <argument name="formBlockType" xsi:type="object">
            Magento\Payment\Block\Form
        </argument>
        <argument name="infoBlockType" xsi:type="string">
            PayPal\Braintree\Block\Info
        </argument>
    </arguments>
</virtualType>

This is a virtual type configuration.

This configuration is for the base area. Base area configurations will apply to all the sub-applications.

This virtualType configuration tells the Object Manager when a user wants a virtual BraintreeLpm object that it should return a Magento\Payment\Model\Method\Adapter object.

This configuration tells the Object Manager that when a user wants a BraintreeLpm object that the following arguments should be used in the foo object's constructor.